Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add notebook guidelines #316

Merged
merged 4 commits into from
Apr 3, 2023
Merged

Conversation

pablo-gar
Copy link
Contributor

Adds a document with a set of editorial guidelines for notebooks (python) and vignettes (R).

An audit of the existing assets must follow upon approval of this PR.

@pablo-gar pablo-gar marked this pull request as ready for review March 30, 2023 05:00
@codecov
Copy link

codecov bot commented Mar 30, 2023

Codecov Report

Merging #316 (ddaad60) into main (737f270) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #316   +/-   ##
=======================================
  Coverage   91.78%   91.78%           
=======================================
  Files          43       43           
  Lines        2324     2324           
=======================================
  Hits         2133     2133           
  Misses        191      191           
Flag Coverage Δ
unittests 91.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

Copy link
Contributor

@bkmartinjr bkmartinjr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend adding a policy around link-out to documentation. Most notebooks would be more useful if they copiously link to supporting docs (e.g., API), but also may then require ongoing link maintenance as docs evolve.

Otherwise LGTM

Copy link
Collaborator

@atolopko-czi atolopko-czi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with a few typos to correct.

Should this also specify:

  • Results should be run/rendered in the notebook
  • Notebooks should be runnable on instances of type T (CPU/mem), not taking more than M minutes.
  • Code formatting must pass lint requirements (we get this automatically, but still, it's a policy)
  • Python version min/max
  • Must only use packages listed requirements-notebooks.txt

docs/cell_census_notebook_guidelines.md Outdated Show resolved Hide resolved
docs/cell_census_notebook_guidelines.md Outdated Show resolved Hide resolved
docs/cell_census_notebook_guidelines.md Outdated Show resolved Hide resolved
pablo-gar and others added 3 commits April 3, 2023 12:25
Co-authored-by: Andrew Tolopko <[email protected]>
Co-authored-by: Andrew Tolopko <[email protected]>
Co-authored-by: Andrew Tolopko <[email protected]>
@pablo-gar
Copy link
Contributor Author

@bkmartinjr

Recommend adding a policy around link-out to documentation.

These will live in doc-site and should mainly be accessed through doc-site, no user-facing docs should link to the notebooks in the repo. Adding the doc-site link will be redundant

@pablo-gar pablo-gar merged commit c9a5756 into main Apr 3, 2023
@pablo-gar pablo-gar deleted the pablo-gar/add-notebook-guidelines branch April 3, 2023 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants